test(connectivity_plus): update android version boundary to accommodate API 24 emulator behavior#3857
Merged
vbuberen merged 1 commit intoJun 18, 2026
Conversation
vbuberen
approved these changes
Jun 18, 2026
…te API 24 emulator behavior
vbuberen
force-pushed
the
fix/connectivity-test-api24-threshold
branch
from
31237a3 to
10cc1e2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR resolves the pre-existing integration test failures on Android API Level 24 by updating the operating system version skip threshold from 5 to 7.
On emulators running API levels lower than 25 (Android 7.1), the environment does not automatically provision a simulated Wi-Fi access point (
AndroidWifi). Because the suite tests for an active Wi-Fi connection, this limitation causes fail on legacy test matrices (such as our API 24 runner).Related Issues
See also this explanation from #3849
Checklist
CHANGELOG.mdnor the plugin version inpubspec.yamlfiles.flutter analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?